chore: Replace bitnamilegacy/kafka with soldevelo/kafka (actively maintained fork) #7458
+20
−20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jkondrat-sd
requested review from
3vilhamster,
Shaddoll,
davidporter-id-au,
demirkayaender,
dkrotx,
jakobht,
neil-xie,
sankari165,
shijiesheng and
taylanisikdemir
as code owners
jkondrat-sd
changed the title
… fork) Signed-off-by: Jakub Kondrat <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Replaced
bitnamilegacy/kafka:3.7withsoldevelo/kafka:3.7in the Docker configuration. The Soldevelo image is a fully compatible, actively maintained fork.https://hub.docker.com/r/soldevelo/kafka/
https://github.com/SolDevelo/containers
Why?
The Bitnami legacy Kafka image is outdated and no longer maintained. Soldevelo provides a drop-in replacement that remains open-source, actively supported, and avoids the limitations of the legacy image. This follows the earlier note that Bitnami Legacy was only a temporary workaround until an open-source alternative was selected.
How did you test it?
Tested locally via Docker Compose to confirm compatibility with the previous Bitnami image.
Potential risks
No risks expected. The Kafka version remains the same and the image is a drop-in replacement.
Release notes
No updates required.
Documentation Changes
None required; configuration remains unchanged.